Problem

Refreshing the mod list in GUI involves two steps:

1. Getting the new data from the server
2. Updating the lists and filters

Step 2 can take several seconds. While it's happening, the window freezes, because the intensive processing is done on the GUI thread (whereas step 1 has a progress bar). The freeze also happens when switching instances and changing version compatibility.

Changes

Now while the mod list is loading, the processing takes place in a background thread, and the progress bar screen is shown with messages indicating which step we're on (helpful for identifying slow pieces!):

This keeps the UI responsive and assures the user that it hasn't crashed. When finished, the tab is hidden.

Side performance tweak

While implementing this, I found out that the slowest step is Registry.Available, with a typical run time of up to a few seconds (I thought it would be loading the data from the registry.json file).

Unrelated to the above changes, this function was always called at the end of a repo update, but that was just to generate an int return value that isn't even used most of the time. So now those functions return bool and just return true instead of calling Registry.Available, and calling code is updated to call Registry.Available when it's actually needed. This should slightly speed up refreshes in GUI.